Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe17c9e751edcef846de58799f01e5b17075e7d5b3765e98e8303a7ffda45bb9

Tx prefix hash: bbd6f85b6e7da07462df1cba67f6395c5817651c62aed2541649c27d7ed5c5ac
Tx public key: 2cdd81715eb0500959ad90675e1e2db54f218f0ce707ffb4c8332c00cff7e1f8
Timestamp: 1719815408 Timestamp [UCT]: 2024-07-01 06:30:08 Age [y:d:h:m:s]: 01:180:10:31:55
Block: 1056019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387565 RingCT/type: yes/0
Extra: 012cdd81715eb0500959ad90675e1e2db54f218f0ce707ffb4c8332c00cff7e1f802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11876b62b2c451ebe27c9a73cd06a6faa76c48f70db481244f67a67f9249df50 0.600000000000 1526430 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": 1056029, "vin": [ { "gen": { "height": 1056019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11876b62b2c451ebe27c9a73cd06a6faa76c48f70db481244f67a67f9249df50" } } ], "extra": [ 1, 44, 221, 129, 113, 94, 176, 80, 9, 89, 173, 144, 103, 94, 30, 45, 181, 79, 33, 143, 12, 231, 7, 255, 180, 200, 51, 44, 0, 207, 247, 225, 248, 2, 17, 0, 0, 0, 2, 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