Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0bfa924cf32fedc74691d6bf20e1cb3991e1eb355521a04937044f58f6c61904

Tx prefix hash: e0e83eb00a8f1ae4575b892cd66a5e2f37d9a95fb2df31cea921a2ca0a630ffa
Tx public key: 3e126d10f0d0245b95bc8d39458a1c4d58f32e84d69793fdf3a29e96e9388d0d
Timestamp: 1729196910 Timestamp [UCT]: 2024-10-17 20:28:30 Age [y:d:h:m:s]: 00:021:07:04:07
Block: 1133805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15171 RingCT/type: yes/0
Extra: 013e126d10f0d0245b95bc8d39458a1c4d58f32e84d69793fdf3a29e96e9388d0d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4db251c00bd4e0cf17b38f5f41323fc9892bf8d566cc421ef406ec503c816c48 0.600000000000 1617008 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1133815, "vin": [ { "gen": { "height": 1133805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4db251c00bd4e0cf17b38f5f41323fc9892bf8d566cc421ef406ec503c816c48" } } ], "extra": [ 1, 62, 18, 109, 16, 240, 208, 36, 91, 149, 188, 141, 57, 69, 138, 28, 77, 88, 243, 46, 132, 214, 151, 147, 253, 243, 162, 158, 150, 233, 56, 141, 13, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8