Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 810e789dcb2424bea1fd36161ce2dc19c3955194f2de0e7043e3c856712197ae

Tx prefix hash: 673a6b248c479461e5e1e5fe4886805e5337a352906f9accd8aec0e40d97f433
Tx public key: 0a4e31011d53cccec9a6d2dd6f7fdc2b1d417b3aabf839d1ba318dbc05bf4e6e
Timestamp: 1734871934 Timestamp [UCT]: 2024-12-22 12:52:14 Age [y:d:h:m:s]: 00:177:22:10:08
Block: 1180757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126856 RingCT/type: yes/0
Extra: 010a4e31011d53cccec9a6d2dd6f7fdc2b1d417b3aabf839d1ba318dbc05bf4e6e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd153afdb21b174a25c4e4b07684437c0ffe542f8cdaa9e2648bb5ba635f237b 0.600000000000 1667170 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": 1180767, "vin": [ { "gen": { "height": 1180757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd153afdb21b174a25c4e4b07684437c0ffe542f8cdaa9e2648bb5ba635f237b" } } ], "extra": [ 1, 10, 78, 49, 1, 29, 83, 204, 206, 201, 166, 210, 221, 111, 127, 220, 43, 29, 65, 123, 58, 171, 248, 57, 209, 186, 49, 141, 188, 5, 191, 78, 110, 2, 17, 0, 0, 0, 5, 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