Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7bd2b1324ebbbc20c037fad4902fb9f5503bae0d216c0521642b2a3fcfde847

Tx prefix hash: 337ccd22f160dcfb661301864996470bc98b16e3fdb3670680cfb07164a9dd30
Tx public key: 3f428fa84bbb9f84e04b2d272ccafcc8af7fb6109b80a9b2633f9d517f3ecbad
Timestamp: 1703979298 Timestamp [UCT]: 2023-12-30 23:34:58 Age [y:d:h:m:s]: 01:173:10:36:32
Block: 924727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384955 RingCT/type: yes/0
Extra: 013f428fa84bbb9f84e04b2d272ccafcc8af7fb6109b80a9b2633f9d517f3ecbad02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ad85007e5ec1ceac82c3cdef5a2b42ee61a4368669c06ed630f0dd8234f4948 0.600000000000 1382483 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": 924737, "vin": [ { "gen": { "height": 924727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ad85007e5ec1ceac82c3cdef5a2b42ee61a4368669c06ed630f0dd8234f4948" } } ], "extra": [ 1, 63, 66, 143, 168, 75, 187, 159, 132, 224, 75, 45, 39, 44, 202, 252, 200, 175, 127, 182, 16, 155, 128, 169, 178, 99, 63, 157, 81, 127, 62, 203, 173, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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