Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba4a1ddd48eb683518e67c382b44ad97254c8f45d2d7e50c5aa2c1f5db4b0176

Tx prefix hash: ecdc26956352c54bc49685e09c797d6d1a849a1d3f39f17c06c6d34b43470dd7
Tx public key: f25caa1f1e8eff44284fb1ae813d3d9f11eae4841a9c5951215e0053b8880c54
Timestamp: 1702196845 Timestamp [UCT]: 2023-12-10 08:27:25 Age [y:d:h:m:s]: 01:037:12:18:43
Block: 909965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288160 RingCT/type: yes/0
Extra: 01f25caa1f1e8eff44284fb1ae813d3d9f11eae4841a9c5951215e0053b8880c54021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59062628942a73499d2a34daa6133ea589510afbeb12d1adc48821b2496a9280 0.600000000000 1367102 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": 909975, "vin": [ { "gen": { "height": 909965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59062628942a73499d2a34daa6133ea589510afbeb12d1adc48821b2496a9280" } } ], "extra": [ 1, 242, 92, 170, 31, 30, 142, 255, 68, 40, 79, 177, 174, 129, 61, 61, 159, 17, 234, 228, 132, 26, 156, 89, 81, 33, 94, 0, 83, 184, 136, 12, 84, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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