Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a26eb3e2c5dd43d6f3b11c93e87c3ca352f6c9354afe6eb7be3a8549583867

Tx prefix hash: a84bd0191b0a201789486427401df0cfe52c52089e089e3cd18b2270691c194a
Tx public key: 0d4335dca23e0bba741fbe306945aa8bb4de3331d7d0b7fdb40768e0a2489578
Timestamp: 1733114122 Timestamp [UCT]: 2024-12-02 04:35:22 Age [y:d:h:m:s]: 00:112:14:20:18
Block: 1166180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80265 RingCT/type: yes/0
Extra: 010d4335dca23e0bba741fbe306945aa8bb4de3331d7d0b7fdb40768e0a2489578021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6db4c35db707369f6b54ca253a734a762cfb9c952f3a82f49fd180c923679cf6 0.600000000000 1651857 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": 1166190, "vin": [ { "gen": { "height": 1166180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6db4c35db707369f6b54ca253a734a762cfb9c952f3a82f49fd180c923679cf6" } } ], "extra": [ 1, 13, 67, 53, 220, 162, 62, 11, 186, 116, 31, 190, 48, 105, 69, 170, 139, 180, 222, 51, 49, 215, 208, 183, 253, 180, 7, 104, 224, 162, 72, 149, 120, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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