Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa6f14fc3e17a10d490efa99440bde9807f15a3d9717377450eb0983c170512

Tx prefix hash: 34d30908f21325d596b633072ae10bb9d6ee653c25076adc018e8d5d51cb0789
Tx public key: 87db3be3a66ef383eda917f4020e7b6802537c2d56f265f9e7e3e3f9f1cdeecb
Timestamp: 1747792128 Timestamp [UCT]: 2025-05-21 01:48:48 Age [y:d:h:m:s]: 00:182:20:26:44
Block: 1287436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128376 RingCT/type: yes/0
Extra: 0187db3be3a66ef383eda917f4020e7b6802537c2d56f265f9e7e3e3f9f1cdeecb0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a659fb9914aba9b8e8a37b232d35de91fe90e7fc1c16ba3437fe67c23abc5145 0.600000000000 1774903 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": 1287446, "vin": [ { "gen": { "height": 1287436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a659fb9914aba9b8e8a37b232d35de91fe90e7fc1c16ba3437fe67c23abc5145" } } ], "extra": [ 1, 135, 219, 59, 227, 166, 110, 243, 131, 237, 169, 23, 244, 2, 14, 123, 104, 2, 83, 124, 45, 86, 242, 101, 249, 231, 227, 227, 249, 241, 205, 238, 203, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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