Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d797b5e0ae0fdfecafd8ff72763afca6533f129352ed0b8ecd8becf3cf3a5a3c

Tx prefix hash: b4673b5605d48946d7e751809ef870b12d2b1104a0354f8f09ce6423a8480f19
Tx public key: 90e968f0261014c0ad2edc5be5e3183be7b79f8ad673799d72cad48fd6924483
Timestamp: 1737458659 Timestamp [UCT]: 2025-01-21 11:24:19 Age [y:d:h:m:s]: 00:334:15:19:15
Block: 1202104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236761 RingCT/type: yes/0
Extra: 0190e968f0261014c0ad2edc5be5e3183be7b79f8ad673799d72cad48fd69244830211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a69c5a98ab1699ccd38d5cb2f81f9204e058695837feb11b8be90aa54e4d32 0.600000000000 1688763 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": 1202114, "vin": [ { "gen": { "height": 1202104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a69c5a98ab1699ccd38d5cb2f81f9204e058695837feb11b8be90aa54e4d32" } } ], "extra": [ 1, 144, 233, 104, 240, 38, 16, 20, 192, 173, 46, 220, 91, 229, 227, 24, 59, 231, 183, 159, 138, 214, 115, 121, 157, 114, 202, 212, 143, 214, 146, 68, 131, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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