Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23b1201e745aa9d0bcbef7f54f0a2aba0d3132786ee290d7a6665b8f6bf66837

Tx prefix hash: 7f7814dd9bf7457427d5f986bdd3508be614e410992a678a12bda63cb087153e
Tx public key: 25a85a2a7df8b906e7342cca3f53a1a7296462cd8e9f54fc23c63a6aafaad47c
Timestamp: 1718374278 Timestamp [UCT]: 2024-06-14 14:11:18 Age [y:d:h:m:s]: 00:205:18:43:58
Block: 1044088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147266 RingCT/type: yes/0
Extra: 0125a85a2a7df8b906e7342cca3f53a1a7296462cd8e9f54fc23c63a6aafaad47c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b62934965bc316cb6f4eceeb0fac6ee77efb2dd8924a7b73a5b54d91898742eb 0.600000000000 1513297 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": 1044098, "vin": [ { "gen": { "height": 1044088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b62934965bc316cb6f4eceeb0fac6ee77efb2dd8924a7b73a5b54d91898742eb" } } ], "extra": [ 1, 37, 168, 90, 42, 125, 248, 185, 6, 231, 52, 44, 202, 63, 83, 161, 167, 41, 100, 98, 205, 142, 159, 84, 252, 35, 198, 58, 106, 175, 170, 212, 124, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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