Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b597996db9cdaa1c7eea79f864440cb0ea2daed290e48825ff9e7503b2836bcf

Tx prefix hash: e5fc17be8154be1e82e3964cef4b188b312d2f5513a717ce849665f2d9f87d2a
Tx public key: 34c3632df45b01a8ef9d0599bee5142585f4a03d9b857462eeb7bde80465a384
Timestamp: 1739119500 Timestamp [UCT]: 2025-02-09 16:45:00 Age [y:d:h:m:s]: 00:328:23:29:08
Block: 1215639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232951 RingCT/type: yes/0
Extra: 0134c3632df45b01a8ef9d0599bee5142585f4a03d9b857462eeb7bde80465a384021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a68d44dcab3f0bde28b69f48d142d0a89afbf71b8ce01861f6c7f668738576d6 0.600000000000 1702438 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": 1215649, "vin": [ { "gen": { "height": 1215639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a68d44dcab3f0bde28b69f48d142d0a89afbf71b8ce01861f6c7f668738576d6" } } ], "extra": [ 1, 52, 195, 99, 45, 244, 91, 1, 168, 239, 157, 5, 153, 190, 229, 20, 37, 133, 244, 160, 61, 155, 133, 116, 98, 238, 183, 189, 232, 4, 101, 163, 132, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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