Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034df7f740014fcebecf687cd7af98598d96c3c49e83618703b823f64ae10f7e

Tx prefix hash: ee934eb50dce3dec2852a1161004434f3cea2643e377b391e8e7c90444b69773
Tx public key: b43d2df9d00e7de2b56f4d1358ce2c7d524b42113cfd39e8abd6fe9e4cb76b4d
Timestamp: 1708316152 Timestamp [UCT]: 2024-02-19 04:15:52 Age [y:d:h:m:s]: 01:324:01:18:55
Block: 960691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490432 RingCT/type: yes/0
Extra: 01b43d2df9d00e7de2b56f4d1358ce2c7d524b42113cfd39e8abd6fe9e4cb76b4d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a4b088b28bcd6c29497655287a6694e90a46c58c190f733cbcdbf0edc26e2b5 0.600000000000 1420278 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": 960701, "vin": [ { "gen": { "height": 960691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a4b088b28bcd6c29497655287a6694e90a46c58c190f733cbcdbf0edc26e2b5" } } ], "extra": [ 1, 180, 61, 45, 249, 208, 14, 125, 226, 181, 111, 77, 19, 88, 206, 44, 125, 82, 75, 66, 17, 60, 253, 57, 232, 171, 214, 254, 158, 76, 183, 107, 77, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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