Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 107a3d4c42295125daa3c8eb7f5db611be05423bd56c186693d955554068c2a5

Tx prefix hash: bc6ebecd025026f646e2a90d410fdb1808eabbff1213201f0fd4af32a00a949a
Tx public key: 271d450ad12752f84ec470b738d9496e19c37ea25bdc75fbb16cd4a40712de39
Timestamp: 1575059692 Timestamp [UCT]: 2019-11-29 20:34:52 Age [y:d:h:m:s]: 05:140:15:26:21
Block: 20024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1243384 RingCT/type: yes/0
Extra: 01271d450ad12752f84ec470b738d9496e19c37ea25bdc75fbb16cd4a40712de3902110000001cad433a0b000000000000000000

1 output(s) for total of 526.808838184000 dcy

stealth address amount amount idx
00: bb8bfe4480d813d784d0c6ba9f88d999ee1a06dfbc9e3dbf3e00cd6f8330bc05 526.808838184000 31960 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": 20034, "vin": [ { "gen": { "height": 20024 } } ], "vout": [ { "amount": 526808838184, "target": { "key": "bb8bfe4480d813d784d0c6ba9f88d999ee1a06dfbc9e3dbf3e00cd6f8330bc05" } } ], "extra": [ 1, 39, 29, 69, 10, 209, 39, 82, 248, 78, 196, 112, 183, 56, 217, 73, 110, 25, 195, 126, 162, 91, 220, 117, 251, 177, 108, 212, 164, 7, 18, 222, 57, 2, 17, 0, 0, 0, 28, 173, 67, 58, 11, 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