Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d7372309ae37f5ff35d798e0781ae4d0ebedbde25e973987c6879b600d247c

Tx prefix hash: 810e69a4f378f0b846f434bcfb759346441b17f430e667277efcb0e7a76e2fd6
Tx public key: d630f6d9b97f715c1b8024e0a849a69e3ad5114b5e321839cc0422881ac36163
Timestamp: 1710361383 Timestamp [UCT]: 2024-03-13 20:23:03 Age [y:d:h:m:s]: 01:060:10:21:48
Block: 977668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304179 RingCT/type: yes/0
Extra: 01d630f6d9b97f715c1b8024e0a849a69e3ad5114b5e321839cc0422881ac361630211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 815f74d822a4e1fcc4154791a105176786f6a2af35dc5de60a38a92fcaf17cda 0.600000000000 1437671 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": 977678, "vin": [ { "gen": { "height": 977668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "815f74d822a4e1fcc4154791a105176786f6a2af35dc5de60a38a92fcaf17cda" } } ], "extra": [ 1, 214, 48, 246, 217, 185, 127, 113, 92, 27, 128, 36, 224, 168, 73, 166, 158, 58, 213, 17, 75, 94, 50, 24, 57, 204, 4, 34, 136, 26, 195, 97, 99, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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