Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60cca9868ea7afbc96ea7a00d04ee2baeed76fe1cefed053504523a822b51698

Tx prefix hash: f8977d4ed2f90972f592f93678829fa8d0e8afffa975c5b6cee504735ee42e0b
Tx public key: 7a2b9ff06a89e88a6cecc5ed021c3e03fd3cf7b7b1ca5eaaaeb4ab0d7a2a8b22
Timestamp: 1725459020 Timestamp [UCT]: 2024-09-04 14:10:20 Age [y:d:h:m:s]: 00:126:18:36:23
Block: 1102825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90660 RingCT/type: yes/0
Extra: 017a2b9ff06a89e88a6cecc5ed021c3e03fd3cf7b7b1ca5eaaaeb4ab0d7a2a8b2202110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd1b56a6af26ed8ca39a88cb12c3cf88f98f6d531656ce1f7390ba4afa20135b 0.600000000000 1579408 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": 1102835, "vin": [ { "gen": { "height": 1102825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd1b56a6af26ed8ca39a88cb12c3cf88f98f6d531656ce1f7390ba4afa20135b" } } ], "extra": [ 1, 122, 43, 159, 240, 106, 137, 232, 138, 108, 236, 197, 237, 2, 28, 62, 3, 253, 60, 247, 183, 177, 202, 94, 170, 174, 180, 171, 13, 122, 42, 139, 34, 2, 17, 0, 0, 0, 12, 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