Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd529321bd6beab86a17b304e3a42cfc666099fc358d5ac04dddec7281095e3

Tx prefix hash: 208229c081266e1f3f7e6f27e7d3b8727afdbd277038291cb6cec16e353b0e22
Tx public key: c770a6715c46380413864558730046df4dadb2966d69efa8da65f3a3e42e5e52
Timestamp: 1718078561 Timestamp [UCT]: 2024-06-11 04:02:41 Age [y:d:h:m:s]: 00:286:20:38:14
Block: 1041634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204974 RingCT/type: yes/0
Extra: 01c770a6715c46380413864558730046df4dadb2966d69efa8da65f3a3e42e5e520211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60818c4dcb7a77aa4f509c5676ae7d2aaf53023fdac724c2bb1021f286ae165c 0.600000000000 1510355 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": 1041644, "vin": [ { "gen": { "height": 1041634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60818c4dcb7a77aa4f509c5676ae7d2aaf53023fdac724c2bb1021f286ae165c" } } ], "extra": [ 1, 199, 112, 166, 113, 92, 70, 56, 4, 19, 134, 69, 88, 115, 0, 70, 223, 77, 173, 178, 150, 109, 105, 239, 168, 218, 101, 243, 163, 228, 46, 94, 82, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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