Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83c35b6407b3732b7bfb202e1e0c38197325d684eb9ed15f7be30b4abda9ca86

Tx prefix hash: 5e0145c80a42c370cc4006ee78a8f0182ea500eb0b7a9cd91cf3e9ab7aec8209
Tx public key: d646677787c4f674aa295c89ae8c4b85adbcdaf813d54cf261120a14d1b119c9
Timestamp: 1708464189 Timestamp [UCT]: 2024-02-20 21:23:09 Age [y:d:h:m:s]: 01:259:06:37:29
Block: 961910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444036 RingCT/type: yes/0
Extra: 01d646677787c4f674aa295c89ae8c4b85adbcdaf813d54cf261120a14d1b119c902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0a43ff5cf91144795025918faf3f270636097f47fa220a6c511c7dc2e6c9a6 0.600000000000 1421527 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": 961920, "vin": [ { "gen": { "height": 961910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0a43ff5cf91144795025918faf3f270636097f47fa220a6c511c7dc2e6c9a6" } } ], "extra": [ 1, 214, 70, 103, 119, 135, 196, 246, 116, 170, 41, 92, 137, 174, 140, 75, 133, 173, 188, 218, 248, 19, 213, 76, 242, 97, 18, 10, 20, 209, 177, 25, 201, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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