Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6529f4ae6deb5a7fa1323a2c0f23ec28a4e264969d4875c26baafc40c0f6fb8f

Tx prefix hash: 08ca12b4616ec8028c4236175640934780e9966496cf63714a652c2cc8a376bc
Tx public key: dd89bb82f4c5c94449384a4561ff5331fea3b21b63e15eacf1dd65499453d0af
Timestamp: 1699635806 Timestamp [UCT]: 2023-11-10 17:03:26 Age [y:d:h:m:s]: 01:102:03:23:34
Block: 888732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334139 RingCT/type: yes/0
Extra: 01dd89bb82f4c5c94449384a4561ff5331fea3b21b63e15eacf1dd65499453d0af021100000010e6d27f9c000000000000000000

1 output(s) for total of 0.697046826000 dcy

stealth address amount amount idx
00: 9c398b4dc2ff432e4b244f36030a9fd78702ad77ecc60df1564d98827ce79c8c 0.697046826000 1344689 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": 888742, "vin": [ { "gen": { "height": 888732 } } ], "vout": [ { "amount": 697046826, "target": { "key": "9c398b4dc2ff432e4b244f36030a9fd78702ad77ecc60df1564d98827ce79c8c" } } ], "extra": [ 1, 221, 137, 187, 130, 244, 197, 201, 68, 73, 56, 74, 69, 97, 255, 83, 49, 254, 163, 178, 27, 99, 225, 94, 172, 241, 221, 101, 73, 148, 83, 208, 175, 2, 17, 0, 0, 0, 16, 230, 210, 127, 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