Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c51391bef65035658affc8d89accf4e5fe8aeeb46ca4ab32444377d12de323f

Tx prefix hash: afa640a520c9b9951f567ef60efcdf8c932e2b777ce35e35eaf277eb5eaa9a5a
Tx public key: df0aaa29ff713e83bd136b8a642175d4bd811f5f12a7cafa827921fbde6d519a
Timestamp: 1739975397 Timestamp [UCT]: 2025-02-19 14:29:57 Age [y:d:h:m:s]: 00:230:14:30:16
Block: 1222693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162524 RingCT/type: yes/0
Extra: 01df0aaa29ff713e83bd136b8a642175d4bd811f5f12a7cafa827921fbde6d519a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 687b9dbc761dd9c1c06ad704c51c560cf85fd5715ee7f753e7caf6212c8411c2 0.600000000000 1709546 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": 1222703, "vin": [ { "gen": { "height": 1222693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "687b9dbc761dd9c1c06ad704c51c560cf85fd5715ee7f753e7caf6212c8411c2" } } ], "extra": [ 1, 223, 10, 170, 41, 255, 113, 62, 131, 189, 19, 107, 138, 100, 33, 117, 212, 189, 129, 31, 95, 18, 167, 202, 250, 130, 121, 33, 251, 222, 109, 81, 154, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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