Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8426f87f02b5fe1520b5c1b1a977f4dbcc966932125c7f893608a0e2d0d0580

Tx prefix hash: b475e9a9439a13aaf57135dd8e2ee588e6ba838c20d9a3a4d1c01a1f387fbf9e
Tx public key: 7cb27456485c332e810c04327ca0bb456a5158be68f6314a9faec8dbc233ebe0
Timestamp: 1728997261 Timestamp [UCT]: 2024-10-15 13:01:01 Age [y:d:h:m:s]: 00:087:03:30:08
Block: 1132152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62271 RingCT/type: yes/0
Extra: 017cb27456485c332e810c04327ca0bb456a5158be68f6314a9faec8dbc233ebe002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2bb12dd5f603f1c903b9ffaa62da5b8191582b9c44d5e75a17434b7ff51e97c 0.600000000000 1615065 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": 1132162, "vin": [ { "gen": { "height": 1132152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2bb12dd5f603f1c903b9ffaa62da5b8191582b9c44d5e75a17434b7ff51e97c" } } ], "extra": [ 1, 124, 178, 116, 86, 72, 92, 51, 46, 129, 12, 4, 50, 124, 160, 187, 69, 106, 81, 88, 190, 104, 246, 49, 74, 159, 174, 200, 219, 194, 51, 235, 224, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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