Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5e59e17d5f8ab4e5e7c3c3559361d32e5d560fa26c3c1a129f222a6aa19b16d

Tx prefix hash: ff0f0eb7b94fa3f0242d4873313167c252386b7e9126436cd84a220fd6615f42
Tx public key: e62cbcefb167502c896cb3139b029c9cd126b578cbb88666e5eb4231fce636ad
Timestamp: 1725452477 Timestamp [UCT]: 2024-09-04 12:21:17 Age [y:d:h:m:s]: 00:109:16:23:48
Block: 1102760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78475 RingCT/type: yes/0
Extra: 01e62cbcefb167502c896cb3139b029c9cd126b578cbb88666e5eb4231fce636ad02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67b402010a447eee6fc0c1dc3a36e3adf90347665d5f4d200bf8bfd539a57b5a 0.600000000000 1579323 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": 1102770, "vin": [ { "gen": { "height": 1102760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67b402010a447eee6fc0c1dc3a36e3adf90347665d5f4d200bf8bfd539a57b5a" } } ], "extra": [ 1, 230, 44, 188, 239, 177, 103, 80, 44, 137, 108, 179, 19, 155, 2, 156, 156, 209, 38, 181, 120, 203, 184, 134, 102, 229, 235, 66, 49, 252, 230, 54, 173, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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