Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b13edd00ddeda9f3b6160ca983d26d329e646ec42f927b9cfcc5aa2b013274e

Tx prefix hash: 5c921c5469454e7b9e5c7e59c77682b4082dd799f05e5cc8e32b48b8783d1520
Tx public key: 8df67520dca1ea59d06f1b2c63949492a3d749574b502cb54bcebb4a2ce090ac
Timestamp: 1574721053 Timestamp [UCT]: 2019-11-25 22:30:53 Age [y:d:h:m:s]: 05:186:10:02:32
Block: 17472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1275897 RingCT/type: yes/0
Extra: 018df67520dca1ea59d06f1b2c63949492a3d749574b502cb54bcebb4a2ce090ac021100000001f95225a5000000000000000000

1 output(s) for total of 537.166464355000 dcy

stealth address amount amount idx
00: 7cafeb26bafc4bf47f36a7d1c70f8b2bf39513d08894f68edd819e21a46f5354 537.166464355000 25445 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": 17482, "vin": [ { "gen": { "height": 17472 } } ], "vout": [ { "amount": 537166464355, "target": { "key": "7cafeb26bafc4bf47f36a7d1c70f8b2bf39513d08894f68edd819e21a46f5354" } } ], "extra": [ 1, 141, 246, 117, 32, 220, 161, 234, 89, 208, 111, 27, 44, 99, 148, 148, 146, 163, 215, 73, 87, 75, 80, 44, 181, 75, 206, 187, 74, 44, 224, 144, 172, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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