Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2506226188c171e66e77bb5e5c6f431f77fd59bfe339e39118f7d8e821f7f4b

Tx prefix hash: 7612bcaceb59d8329f72719d18e42d665a6032554e17766f6330b5ec82e3ee8b
Tx public key: 6e321fb8c465b17baa444505f7125d8fd5e325636bdfde5adb745e311d5f5b57
Timestamp: 1710672755 Timestamp [UCT]: 2024-03-17 10:52:35 Age [y:d:h:m:s]: 01:020:14:33:48
Block: 980245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275682 RingCT/type: yes/0
Extra: 016e321fb8c465b17baa444505f7125d8fd5e325636bdfde5adb745e311d5f5b5702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8eb1bcaa7a88c2a09dab795f8e55236d2eff91b58f9040a13e7131261783222 0.600000000000 1440310 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": 980255, "vin": [ { "gen": { "height": 980245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8eb1bcaa7a88c2a09dab795f8e55236d2eff91b58f9040a13e7131261783222" } } ], "extra": [ 1, 110, 50, 31, 184, 196, 101, 177, 123, 170, 68, 69, 5, 247, 18, 93, 143, 213, 227, 37, 99, 107, 223, 222, 90, 219, 116, 94, 49, 29, 95, 91, 87, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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