Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34f32c4efe800cb2bc038c78f2d768f4808aaebbafc320002c480341071fe3ad

Tx prefix hash: fdc65d95667f54fc8d2810204a3370cafb3e3f48a133ee5d60b6c2c834260cb3
Tx public key: 80b3dd73407444a2663b96f94a33d7771128c9b26ce8e3c9f1a34665dd488cbd
Timestamp: 1715488292 Timestamp [UCT]: 2024-05-12 04:31:32 Age [y:d:h:m:s]: 00:260:09:22:23
Block: 1020189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186074 RingCT/type: yes/0
Extra: 0180b3dd73407444a2663b96f94a33d7771128c9b26ce8e3c9f1a34665dd488cbd02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a8c9b29b1ab99d906cafdaf8f46d7f7e3ae97ef9089eec9ecdf7f1cc1002057 0.600000000000 1484250 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": 1020199, "vin": [ { "gen": { "height": 1020189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a8c9b29b1ab99d906cafdaf8f46d7f7e3ae97ef9089eec9ecdf7f1cc1002057" } } ], "extra": [ 1, 128, 179, 221, 115, 64, 116, 68, 162, 102, 59, 150, 249, 74, 51, 215, 119, 17, 40, 201, 178, 108, 232, 227, 201, 241, 163, 70, 101, 221, 72, 140, 189, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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