Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4641613b836036525f45c2d2bba0eddd493ae1e99505729505ef128410f49044

Tx prefix hash: 3fde5b7254649dfb7ba21299152048b4dfd0407b498c904c11cad64a062ef076
Tx public key: 55366f2e9a5e6c559049ce4340a8208d88269ef3ed4b364a3f74763e2d504e8c
Timestamp: 1711762998 Timestamp [UCT]: 2024-03-30 01:43:18 Age [y:d:h:m:s]: 01:064:12:39:13
Block: 989285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307110 RingCT/type: yes/0
Extra: 0155366f2e9a5e6c559049ce4340a8208d88269ef3ed4b364a3f74763e2d504e8c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8a859ebe351b637c387ae40eebee5a51a7d5b57f459bc4fdc17818e26448c42 0.600000000000 1449580 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": 989295, "vin": [ { "gen": { "height": 989285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8a859ebe351b637c387ae40eebee5a51a7d5b57f459bc4fdc17818e26448c42" } } ], "extra": [ 1, 85, 54, 111, 46, 154, 94, 108, 85, 144, 73, 206, 67, 64, 168, 32, 141, 136, 38, 158, 243, 237, 75, 54, 74, 63, 116, 118, 62, 45, 80, 78, 140, 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