Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396846933e35d4748e8969381b7fc2a34cdc4a42f3d8a482efeed3c3f435b227

Tx prefix hash: 3d02f84adfc4129395484cb4bd63a65676bb0d0f5926574b6a1aff9d39fa0b4b
Tx public key: 2bb01fa819a2f4869bb5692a9bc4fdbfc12ff1c2a15bc5ed4a0ffdae9ae15804
Timestamp: 1737222942 Timestamp [UCT]: 2025-01-18 17:55:42 Age [y:d:h:m:s]: 00:150:20:15:18
Block: 1200163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107533 RingCT/type: yes/0
Extra: 012bb01fa819a2f4869bb5692a9bc4fdbfc12ff1c2a15bc5ed4a0ffdae9ae158040211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b59fef2a48a38b47e5b5d19e679074dd53b87877490618b05c9b5260e17463b9 0.600000000000 1686804 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": 1200173, "vin": [ { "gen": { "height": 1200163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b59fef2a48a38b47e5b5d19e679074dd53b87877490618b05c9b5260e17463b9" } } ], "extra": [ 1, 43, 176, 31, 168, 25, 162, 244, 134, 155, 181, 105, 42, 155, 196, 253, 191, 193, 47, 241, 194, 161, 91, 197, 237, 74, 15, 253, 174, 154, 225, 88, 4, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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