Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544b7702292ee6ab08ec02e5c35d2f37b1ab283310653407646df6f05f3c4b56

Tx prefix hash: 9965aa79fa71b1782ddc5e2fe4d81992eadae6feda2f41a866b29529b421c985
Tx public key: fbab79cf4519c1f7242aecd98dc35ad7762eea81e932b52810eeba6de6d4e242
Timestamp: 1730361946 Timestamp [UCT]: 2024-10-31 08:05:46 Age [y:d:h:m:s]: 00:146:01:02:11
Block: 1143390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104186 RingCT/type: yes/0
Extra: 01fbab79cf4519c1f7242aecd98dc35ad7762eea81e932b52810eeba6de6d4e2420211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5dae4b207804d22838733fbad93f4ab66749f583f92417fe68a9e299f2b7b84 0.600000000000 1627257 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": 1143400, "vin": [ { "gen": { "height": 1143390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5dae4b207804d22838733fbad93f4ab66749f583f92417fe68a9e299f2b7b84" } } ], "extra": [ 1, 251, 171, 121, 207, 69, 25, 193, 247, 36, 42, 236, 217, 141, 195, 90, 215, 118, 46, 234, 129, 233, 50, 181, 40, 16, 238, 186, 109, 230, 212, 226, 66, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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