Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f290516fc47da28729c4b571404f9d84fccebf8e18614d856b5f812df421a395

Tx prefix hash: c47ae9429ccc138f9df70ef89212a79b8f32a889bcb40964e5a5f8e37886cb39
Tx public key: 2d256834c2d2c0f00134424b1d724788fc88f883dca64c70c79794f5affb088c
Timestamp: 1702979626 Timestamp [UCT]: 2023-12-19 09:53:46 Age [y:d:h:m:s]: 01:121:04:53:44
Block: 916451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347761 RingCT/type: yes/0
Extra: 012d256834c2d2c0f00134424b1d724788fc88f883dca64c70c79794f5affb088c021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1814f08d1725ad611cee1ef99b6a8a2b64e50e761878b53f85225e4276198ce 0.600000000000 1374003 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": 916461, "vin": [ { "gen": { "height": 916451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1814f08d1725ad611cee1ef99b6a8a2b64e50e761878b53f85225e4276198ce" } } ], "extra": [ 1, 45, 37, 104, 52, 194, 210, 192, 240, 1, 52, 66, 75, 29, 114, 71, 136, 252, 136, 248, 131, 220, 166, 76, 112, 199, 151, 148, 245, 175, 251, 8, 140, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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