Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 054a6331bb2bd85c9bd14e239b711ea665232306ab832e8d92c8624dce3882a0

Tx prefix hash: db9bc8d70cf80d1dd470bc9cc0ed75d823f84ca9e48cf6066d133a669f2f6fe9
Tx public key: 5df83aa0b17c0ecf9898cf0a0eeda7b2d94ca9bded9037b959fd414a1dc0ea48
Timestamp: 1682208434 Timestamp [UCT]: 2023-04-23 00:07:14 Age [y:d:h:m:s]: 01:275:09:41:36
Block: 744489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458284 RingCT/type: yes/0
Extra: 015df83aa0b17c0ecf9898cf0a0eeda7b2d94ca9bded9037b959fd414a1dc0ea48021100000003e7ace25d000000000000000000

1 output(s) for total of 2.095072721000 dcy

stealth address amount amount idx
00: bc59b7a96d055fa5e66d1514587bd727b96293077cce649962cef4cde8aa2680 2.095072721000 1191816 of 0

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": 744499, "vin": [ { "gen": { "height": 744489 } } ], "vout": [ { "amount": 2095072721, "target": { "key": "bc59b7a96d055fa5e66d1514587bd727b96293077cce649962cef4cde8aa2680" } } ], "extra": [ 1, 93, 248, 58, 160, 177, 124, 14, 207, 152, 152, 207, 10, 14, 237, 167, 178, 217, 76, 169, 189, 237, 144, 55, 185, 89, 253, 65, 74, 29, 192, 234, 72, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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