Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4456dedc2f849b60186d1c88b6ab0c2cff2eb85a335d12faaa1bcd92d5b07a23

Tx prefix hash: f5f1132103047d103e5cc3bca6b1758184e8203c88e9a07b795520bdd63f577a
Tx public key: 1ba09af45179f1cf89bf2f5d46481202c5bbfa3cd2359dcf430f2a2a825edafd
Timestamp: 1695232022 Timestamp [UCT]: 2023-09-20 17:47:02 Age [y:d:h:m:s]: 01:217:01:15:49
Block: 852410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416216 RingCT/type: yes/0
Extra: 011ba09af45179f1cf89bf2f5d46481202c5bbfa3cd2359dcf430f2a2a825edafd021100000004faf35c9c000000000000000000

1 output(s) for total of 0.919627333000 dcy

stealth address amount amount idx
00: 3e159b369638e3e35776308d312a63b9a557b4b963db31f3b64dc6680aad8621 0.919627333000 1306248 of 0

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": 852420, "vin": [ { "gen": { "height": 852410 } } ], "vout": [ { "amount": 919627333, "target": { "key": "3e159b369638e3e35776308d312a63b9a557b4b963db31f3b64dc6680aad8621" } } ], "extra": [ 1, 27, 160, 154, 244, 81, 121, 241, 207, 137, 191, 47, 93, 70, 72, 18, 2, 197, 187, 250, 60, 210, 53, 157, 207, 67, 15, 42, 42, 130, 94, 218, 253, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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