Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 745ca2fbc9d29f229c14e62f5300076de541121b9d21dede4cae2094fd55f9fb

Tx prefix hash: 13d78022128677779a75f4dc57cd829d3d2b3f72fae6924474f1bf427a71e688
Tx public key: 8af33b7152db2ff2ea72a096b6079e917535f6d81e97bb3a2314b5fa54fb14f4
Timestamp: 1694428245 Timestamp [UCT]: 2023-09-11 10:30:45 Age [y:d:h:m:s]: 01:204:06:43:14
Block: 845734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407098 RingCT/type: yes/0
Extra: 018af33b7152db2ff2ea72a096b6079e917535f6d81e97bb3a2314b5fa54fb14f402110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.967681058000 dcy

stealth address amount amount idx
00: 37f78b5e7b428ffb268328a35d3ecb3d90ddce1f8a4e1bfb9af0b247f7786d10 0.967681058000 1299150 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": 845744, "vin": [ { "gen": { "height": 845734 } } ], "vout": [ { "amount": 967681058, "target": { "key": "37f78b5e7b428ffb268328a35d3ecb3d90ddce1f8a4e1bfb9af0b247f7786d10" } } ], "extra": [ 1, 138, 243, 59, 113, 82, 219, 47, 242, 234, 114, 160, 150, 182, 7, 158, 145, 117, 53, 246, 216, 30, 151, 187, 58, 35, 20, 181, 250, 84, 251, 20, 244, 2, 17, 0, 0, 0, 10, 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