Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e219c43f7e41400b90f693b6c932e6819dd5d4db8cb6f5c709e35f4f0ffd02da

Tx prefix hash: 568f385e0323edd0b4f1a454595da6398417e7cba13d83a7405bbdf08ed613f6
Tx public key: 341d2c4dfd713bcd820a814a9d315e270571bd94d99fb567539d4cbf2437a6ca
Timestamp: 1702509275 Timestamp [UCT]: 2023-12-13 23:14:35 Age [y:d:h:m:s]: 01:100:02:23:28
Block: 912546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332674 RingCT/type: yes/0
Extra: 01341d2c4dfd713bcd820a814a9d315e270571bd94d99fb567539d4cbf2437a6ca021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 636af976c8078011d4f71fae2ba4fe4c8044def63ad64a3e846c241ddcbb853d 0.600000000000 1369774 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": 912556, "vin": [ { "gen": { "height": 912546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "636af976c8078011d4f71fae2ba4fe4c8044def63ad64a3e846c241ddcbb853d" } } ], "extra": [ 1, 52, 29, 44, 77, 253, 113, 59, 205, 130, 10, 129, 74, 157, 49, 94, 39, 5, 113, 189, 148, 217, 159, 181, 103, 83, 157, 76, 191, 36, 55, 166, 202, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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