Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52355243774de8770e06d65b155009eb8f6b00332b2399b3c09a91654fe8c13

Tx prefix hash: aec48d654e61063688f0916eccc35bccd5168dfb64780f558c5033b5fd0f2644
Tx public key: 19421c6d6f7a0c7efbb58c2785f7edac671ebe1a2bda47e26f8b2ef8849d313e
Timestamp: 1717903151 Timestamp [UCT]: 2024-06-09 03:19:11 Age [y:d:h:m:s]: 01:151:20:51:32
Block: 1040170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367112 RingCT/type: yes/0
Extra: 0119421c6d6f7a0c7efbb58c2785f7edac671ebe1a2bda47e26f8b2ef8849d313e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce16334b822bbf9e72d426d6d2c1e3e7143e3b61739cada546c4923c693a506 0.600000000000 1508827 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": 1040180, "vin": [ { "gen": { "height": 1040170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce16334b822bbf9e72d426d6d2c1e3e7143e3b61739cada546c4923c693a506" } } ], "extra": [ 1, 25, 66, 28, 109, 111, 122, 12, 126, 251, 181, 140, 39, 133, 247, 237, 172, 103, 30, 190, 26, 43, 218, 71, 226, 111, 139, 46, 248, 132, 157, 49, 62, 2, 17, 0, 0, 0, 3, 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