Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1048834de138a74e1659c878bc4b61c56596bcedce181b252b1e2da530629e

Tx prefix hash: 34dce27086cb93f19f0da04626223a04c72150892f55163fd2b67c81c84acdbf
Tx public key: 4c7efb5586028ab5553ea8f8c2217fdf6d60a03790d06b5ec04ae6d6e198c80b
Timestamp: 1743910130 Timestamp [UCT]: 2025-04-06 03:28:50 Age [y:d:h:m:s]: 00:227:10:43:44
Block: 1255282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160289 RingCT/type: yes/0
Extra: 014c7efb5586028ab5553ea8f8c2217fdf6d60a03790d06b5ec04ae6d6e198c80b0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4df4c507c27ab482a14324464fac413db2757c7ddbae013747911848e0ae320 0.600000000000 1742385 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": 1255292, "vin": [ { "gen": { "height": 1255282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4df4c507c27ab482a14324464fac413db2757c7ddbae013747911848e0ae320" } } ], "extra": [ 1, 76, 126, 251, 85, 134, 2, 138, 181, 85, 62, 168, 248, 194, 33, 127, 223, 109, 96, 160, 55, 144, 208, 107, 94, 192, 74, 230, 214, 225, 152, 200, 11, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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