Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05283aa342edd7269364dc4716b548a67a713b39449a6f7dcb8d574dff8f218

Tx prefix hash: f7100f3cc64798b2fee3b5e119da6ab1ca511bf6afa12f32db3062b95d3feefc
Tx public key: f4516e8d8bcd8260e6008b48ee93b4e0b157e5190594901e3ff40bcb087dbae5
Timestamp: 1577032173 Timestamp [UCT]: 2019-12-22 16:29:33 Age [y:d:h:m:s]: 05:117:06:09:05
Block: 29680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1233326 RingCT/type: yes/0
Extra: 01f4516e8d8bcd8260e6008b48ee93b4e0b157e5190594901e3ff40bcb087dbae50211000000049159db1e000000000000000000

1 output(s) for total of 489.394069221000 dcy

stealth address amount amount idx
00: 1008327950eb4848f0d7bf0fc79ca66b4bff46fb2265db60f8f928236d128a71 489.394069221000 48854 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": 29690, "vin": [ { "gen": { "height": 29680 } } ], "vout": [ { "amount": 489394069221, "target": { "key": "1008327950eb4848f0d7bf0fc79ca66b4bff46fb2265db60f8f928236d128a71" } } ], "extra": [ 1, 244, 81, 110, 141, 139, 205, 130, 96, 230, 0, 139, 72, 238, 147, 180, 224, 177, 87, 229, 25, 5, 148, 144, 30, 63, 244, 11, 203, 8, 125, 186, 229, 2, 17, 0, 0, 0, 4, 145, 89, 219, 30, 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