Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59dbbe5efb08a1b75534c8ab86c51a20db4902f289f40bc1b41540f2509f83b8

Tx prefix hash: 75fef4fed902c887ba24002e9b6d571728575a74e37df027205ed1383791a96e
Tx public key: f3e005b4d14223b6eec74d0c9d1604dc44ea77932ed7b025e1f3a350b3316ff0
Timestamp: 1728428666 Timestamp [UCT]: 2024-10-08 23:04:26 Age [y:d:h:m:s]: 00:157:18:02:12
Block: 1127428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112551 RingCT/type: yes/0
Extra: 01f3e005b4d14223b6eec74d0c9d1604dc44ea77932ed7b025e1f3a350b3316ff002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e73c7639dc6a49c61cb67fd42784793d3dfcbb1b900d6261daceb40614a1737 0.600000000000 1610233 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": 1127438, "vin": [ { "gen": { "height": 1127428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e73c7639dc6a49c61cb67fd42784793d3dfcbb1b900d6261daceb40614a1737" } } ], "extra": [ 1, 243, 224, 5, 180, 209, 66, 35, 182, 238, 199, 77, 12, 157, 22, 4, 220, 68, 234, 119, 147, 46, 215, 176, 37, 225, 243, 163, 80, 179, 49, 111, 240, 2, 17, 0, 0, 0, 2, 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