Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59fbbe410c570bd82a8a85902cced462bc7010db76069312d8c2c6be841476ac

Tx prefix hash: cd2a13757e241d020d47f6832761388f72620778eaacb10d705c1a0d38d6db8d
Tx public key: f05dbe4e2b8622259e0103d9e27fb16fb797ca71aca12d0f6aee796f3dbf2138
Timestamp: 1695641584 Timestamp [UCT]: 2023-09-25 11:33:04 Age [y:d:h:m:s]: 01:191:15:19:41
Block: 855806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398017 RingCT/type: yes/0
Extra: 01f05dbe4e2b8622259e0103d9e27fb16fb797ca71aca12d0f6aee796f3dbf213802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.896106254000 dcy

stealth address amount amount idx
00: 7c3e0185ca56f7c2f1bdd0c2299f6ddb2e8f5fedd61bb802f900b7247c2c6f37 0.896106254000 1309850 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": 855816, "vin": [ { "gen": { "height": 855806 } } ], "vout": [ { "amount": 896106254, "target": { "key": "7c3e0185ca56f7c2f1bdd0c2299f6ddb2e8f5fedd61bb802f900b7247c2c6f37" } } ], "extra": [ 1, 240, 93, 190, 78, 43, 134, 34, 37, 158, 1, 3, 217, 226, 127, 177, 111, 183, 151, 202, 113, 172, 161, 45, 15, 106, 238, 121, 111, 61, 191, 33, 56, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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