Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31cda3b7887ca72c028b26fb31507361d39d8193b5bfb93f207dfc2c26fed091

Tx prefix hash: f90e67fa2cc4bc7d29b52061d18b6dbae83899cb09892fd4d37c31fbf26fdc20
Tx public key: 8162bbcc86a8a30aa01842aa9af9a9e2ab550770e223a6778c482cf4070983c1
Timestamp: 1736525646 Timestamp [UCT]: 2025-01-10 16:14:06 Age [y:d:h:m:s]: 00:153:07:17:20
Block: 1194413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109363 RingCT/type: yes/0
Extra: 018162bbcc86a8a30aa01842aa9af9a9e2ab550770e223a6778c482cf4070983c1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a3cf3d66b31a5c9740c49849e42b16533d66f7651ce3d8b2aa68f6f21ad0e1c 0.600000000000 1680984 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": 1194423, "vin": [ { "gen": { "height": 1194413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a3cf3d66b31a5c9740c49849e42b16533d66f7651ce3d8b2aa68f6f21ad0e1c" } } ], "extra": [ 1, 129, 98, 187, 204, 134, 168, 163, 10, 160, 24, 66, 170, 154, 249, 169, 226, 171, 85, 7, 112, 226, 35, 166, 119, 140, 72, 44, 244, 7, 9, 131, 193, 2, 17, 0, 0, 0, 1, 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