Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64956aa3a19fbdee44ddbfa6863c9c74ef0a115362be5ac7a2670aab701a4be5

Tx prefix hash: 1d56fa2b4b3380603e5b2863d09dd23d1d34526cb39b6075777a5a65f43463dc
Tx public key: 10a2c852786cc2d42fd5ac64c5601e64d590f51e2dc01b003b73a021ef34ddca
Timestamp: 1736236937 Timestamp [UCT]: 2025-01-07 08:02:17 Age [y:d:h:m:s]: 00:100:03:03:37
Block: 1192037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71341 RingCT/type: yes/0
Extra: 0110a2c852786cc2d42fd5ac64c5601e64d590f51e2dc01b003b73a021ef34ddca0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 397fb39258e4d806f68511f8f7f6148d320dac6de6031abedfcf1a196117d514 0.600000000000 1678582 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": 1192047, "vin": [ { "gen": { "height": 1192037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "397fb39258e4d806f68511f8f7f6148d320dac6de6031abedfcf1a196117d514" } } ], "extra": [ 1, 16, 162, 200, 82, 120, 108, 194, 212, 47, 213, 172, 100, 197, 96, 30, 100, 213, 144, 245, 30, 45, 192, 27, 0, 59, 115, 160, 33, 239, 52, 221, 202, 2, 17, 0, 0, 0, 3, 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