Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8738586fff6baf53bbc8de46496547b36b68cda9c234026d5d71e0f717055f06

Tx prefix hash: 3cc1dd1fedfd07916134dc83c1961688c7f6203d8eb8deefc7cee89c95da6a14
Tx public key: 009e5fcd1a268ef82cfd636eb50207d3e8ff79b7dd41173cd46d0c5d4a508ee7
Timestamp: 1719645082 Timestamp [UCT]: 2024-06-29 07:11:22 Age [y:d:h:m:s]: 00:300:06:55:11
Block: 1054611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214592 RingCT/type: yes/0
Extra: 01009e5fcd1a268ef82cfd636eb50207d3e8ff79b7dd41173cd46d0c5d4a508ee702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c63be276becdd6d0072a371f7bcad4e009a342b2160a6aa99c029eb7db18b038 0.600000000000 1524978 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": 1054621, "vin": [ { "gen": { "height": 1054611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c63be276becdd6d0072a371f7bcad4e009a342b2160a6aa99c029eb7db18b038" } } ], "extra": [ 1, 0, 158, 95, 205, 26, 38, 142, 248, 44, 253, 99, 110, 181, 2, 7, 211, 232, 255, 121, 183, 221, 65, 23, 60, 212, 109, 12, 93, 74, 80, 142, 231, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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