Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bd804325d28be7fd2b4c619da6421c1a410b0711a138422bfc12c21a6a30060

Tx prefix hash: d1008d1e74738669d281d7fdd5ea2ed37b0a56f829b16173204ee5647a6697ce
Tx public key: 89a167c77f398b40aa9f2829a3b4c3290ba151ffbeac5e62da647f6895027dc1
Timestamp: 1711849414 Timestamp [UCT]: 2024-03-31 01:43:34 Age [y:d:h:m:s]: 01:008:10:25:05
Block: 989999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266963 RingCT/type: yes/0
Extra: 0189a167c77f398b40aa9f2829a3b4c3290ba151ffbeac5e62da647f6895027dc10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ce0e9f9675f48cabdfda0265e3a1801d75ba27f8b49258a3dccf839d8d0d763 0.600000000000 1450317 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": 990009, "vin": [ { "gen": { "height": 989999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ce0e9f9675f48cabdfda0265e3a1801d75ba27f8b49258a3dccf839d8d0d763" } } ], "extra": [ 1, 137, 161, 103, 199, 127, 57, 139, 64, 170, 159, 40, 41, 163, 180, 195, 41, 11, 161, 81, 255, 190, 172, 94, 98, 218, 100, 127, 104, 149, 2, 125, 193, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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