Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a65b5669bc893d162cfa3dae4fd6ca28060f34c093d28ae06f1d8913ebb980

Tx prefix hash: 7bccd8c367b87cb4378ccf1f48f17bacf6eedc8c9b651871508e3a5149624e08
Tx public key: 6abdd4b9f8ca49d7e0ff8ee59acea1343551c4d09bbb141af68f91357e364fbd
Timestamp: 1718506025 Timestamp [UCT]: 2024-06-16 02:47:05 Age [y:d:h:m:s]: 00:331:09:35:34
Block: 1045185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236832 RingCT/type: yes/0
Extra: 016abdd4b9f8ca49d7e0ff8ee59acea1343551c4d09bbb141af68f91357e364fbd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09992fe2507d40ce1c46f325d1ad96d776108b1f9edb252323e2a9985bc407f7 0.600000000000 1514690 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": 1045195, "vin": [ { "gen": { "height": 1045185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09992fe2507d40ce1c46f325d1ad96d776108b1f9edb252323e2a9985bc407f7" } } ], "extra": [ 1, 106, 189, 212, 185, 248, 202, 73, 215, 224, 255, 142, 229, 154, 206, 161, 52, 53, 81, 196, 208, 155, 187, 20, 26, 246, 143, 145, 53, 126, 54, 79, 189, 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