Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69abab5aa21c7a44d2ca81cf3024bb722eb8eba04e1da21d0350deed9df8ff94

Tx prefix hash: 1c628c5b380955314fb1cfe0e81b0fa23ed232305cf05eeaf856cf46a3454a0e
Tx public key: cc4ee61231f9bf7ceeba73ca0a2a35e932872d79790c5e85ff3e545b79a9cf32
Timestamp: 1714139525 Timestamp [UCT]: 2024-04-26 13:52:05 Age [y:d:h:m:s]: 00:202:10:11:48
Block: 1008968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144913 RingCT/type: yes/0
Extra: 01cc4ee61231f9bf7ceeba73ca0a2a35e932872d79790c5e85ff3e545b79a9cf3202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51bb2e2fa0ab40ed610148453e52677c95c3ce063d27f5ea01719fc183e9c47f 0.600000000000 1470500 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": 1008978, "vin": [ { "gen": { "height": 1008968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51bb2e2fa0ab40ed610148453e52677c95c3ce063d27f5ea01719fc183e9c47f" } } ], "extra": [ 1, 204, 78, 230, 18, 49, 249, 191, 124, 238, 186, 115, 202, 10, 42, 53, 233, 50, 135, 45, 121, 121, 12, 94, 133, 255, 62, 84, 91, 121, 169, 207, 50, 2, 17, 0, 0, 0, 2, 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