Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10678c3132664b88f4b78793514182fa6e65c9e56b2351cb54c19943dd433e8c

Tx prefix hash: 1e0410b19289222ac4356226f5ebd23624cfa800e06bbbf239737183b71c4da9
Tx public key: ed18729392b4ac4cdc0bd7719aa16fe915e9b2912af5a56e4c38b623e6d29c4e
Timestamp: 1715476686 Timestamp [UCT]: 2024-05-12 01:18:06 Age [y:d:h:m:s]: 00:132:06:31:43
Block: 1020084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94716 RingCT/type: yes/0
Extra: 01ed18729392b4ac4cdc0bd7719aa16fe915e9b2912af5a56e4c38b623e6d29c4e021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32426799ac4e7c4aaa60d031494ea5d4f5a1c61afd97dddb75531ef4b9ef0d2f 0.600000000000 1484143 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": 1020094, "vin": [ { "gen": { "height": 1020084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32426799ac4e7c4aaa60d031494ea5d4f5a1c61afd97dddb75531ef4b9ef0d2f" } } ], "extra": [ 1, 237, 24, 114, 147, 146, 180, 172, 76, 220, 11, 215, 113, 154, 161, 111, 233, 21, 233, 178, 145, 42, 245, 165, 110, 76, 56, 182, 35, 230, 210, 156, 78, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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