Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 796c6b13fb82ce48b2e03ada1c700660c0e82fc1f43e45560936854f56e7a817

Tx prefix hash: 7fff75c3f78fb5b3622f13e6c80c6637c4c1f8447a8cf63910133d57d2e9500c
Tx public key: 7ffc8aa6831d849218ce1f09f3f3d477b65d663ffec645370a58925ba519efb2
Timestamp: 1710694160 Timestamp [UCT]: 2024-03-17 16:49:20 Age [y:d:h:m:s]: 01:071:11:05:28
Block: 980424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312076 RingCT/type: yes/0
Extra: 017ffc8aa6831d849218ce1f09f3f3d477b65d663ffec645370a58925ba519efb20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a704ffdfdd8786265cef86caec89620afe606eaaa1be526d12d214fc1bca51b 0.600000000000 1440489 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": 980434, "vin": [ { "gen": { "height": 980424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a704ffdfdd8786265cef86caec89620afe606eaaa1be526d12d214fc1bca51b" } } ], "extra": [ 1, 127, 252, 138, 166, 131, 29, 132, 146, 24, 206, 31, 9, 243, 243, 212, 119, 182, 93, 102, 63, 254, 198, 69, 55, 10, 88, 146, 91, 165, 25, 239, 178, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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