Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398334ba2263f2f7310a69529973c4e921138fe276100a75930d22079926f1fa

Tx prefix hash: d0e52160d7307314d77a20ba5d1fba180018db4dc37194bb5f2382624231368a
Tx public key: e7fa0b24087d86f0478b70af5456ff52f314c3dee4e8fb966b8b1a9c7efb6b20
Timestamp: 1723746805 Timestamp [UCT]: 2024-08-15 18:33:25 Age [y:d:h:m:s]: 00:307:22:17:07
Block: 1088615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219878 RingCT/type: yes/0
Extra: 01e7fa0b24087d86f0478b70af5456ff52f314c3dee4e8fb966b8b1a9c7efb6b20021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf2fbc6ffdf0b338d1c5b2a505bdf5617212426ddc697554ad71bbcf943af02 0.600000000000 1563232 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": 1088625, "vin": [ { "gen": { "height": 1088615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf2fbc6ffdf0b338d1c5b2a505bdf5617212426ddc697554ad71bbcf943af02" } } ], "extra": [ 1, 231, 250, 11, 36, 8, 125, 134, 240, 71, 139, 112, 175, 84, 86, 255, 82, 243, 20, 195, 222, 228, 232, 251, 150, 107, 139, 26, 156, 126, 251, 107, 32, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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