Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f356bbf75f15eafac550f82077e0bf3cb246fe469b7a99114024c32498278f0d

Tx prefix hash: 3c5bc895dd6d944a06fc4cd5334c563bb1ebdae81df2647da768677fe227f814
Tx public key: 6e653d6715747a9207002c766d7bf0c9c6c595273c2b2d4cdbc3eb7ab69f7ec4
Timestamp: 1734114799 Timestamp [UCT]: 2024-12-13 18:33:19 Age [y:d:h:m:s]: 00:098:06:45:57
Block: 1174484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70012 RingCT/type: yes/0
Extra: 016e653d6715747a9207002c766d7bf0c9c6c595273c2b2d4cdbc3eb7ab69f7ec40211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2b2dacde589af0948c509f2b147f91e4f6a85655eaedbe2e476cafc3d5a1b9d 0.600000000000 1660641 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": 1174494, "vin": [ { "gen": { "height": 1174484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2b2dacde589af0948c509f2b147f91e4f6a85655eaedbe2e476cafc3d5a1b9d" } } ], "extra": [ 1, 110, 101, 61, 103, 21, 116, 122, 146, 7, 0, 44, 118, 109, 123, 240, 201, 198, 197, 149, 39, 60, 43, 45, 76, 219, 195, 235, 122, 182, 159, 126, 196, 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