Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e79de67830c1151e5555bcd5ed35004d1fa3cc6d990dbf356db0f32f54ab1909

Tx prefix hash: 5bcc3ae2dadd73021ea9c0a63c8080eb3b69c91069b81a08fb3e6e97c7c9e507
Tx public key: 433c28795d991654a0c6b10bfd3f5905f1ebbd29f188dcee384e9250fe307d92
Timestamp: 1721302989 Timestamp [UCT]: 2024-07-18 11:43:09 Age [y:d:h:m:s]: 00:133:00:35:12
Block: 1068374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95175 RingCT/type: yes/0
Extra: 01433c28795d991654a0c6b10bfd3f5905f1ebbd29f188dcee384e9250fe307d92021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbadc36efa77fe2d7f82d142d5e9503389d0205c78f4b04b07db99eb1f5b514b 0.600000000000 1539451 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": 1068384, "vin": [ { "gen": { "height": 1068374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbadc36efa77fe2d7f82d142d5e9503389d0205c78f4b04b07db99eb1f5b514b" } } ], "extra": [ 1, 67, 60, 40, 121, 93, 153, 22, 84, 160, 198, 177, 11, 253, 63, 89, 5, 241, 235, 189, 41, 241, 136, 220, 238, 56, 78, 146, 80, 254, 48, 125, 146, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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