Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fea90e845d3fc82e8636b27301d5d3107bc1f1ea683d2d9e97350cecf9b2bd9c

Tx prefix hash: f33f5fb7033833d10d3d3952ab806c9991b636d19bf83e83e3bc00f466c848ca
Tx public key: 1f383d986adb20c4e10282837c12388dce6e7b60ca4ca9a5c1be1139e046f03f
Timestamp: 1745591797 Timestamp [UCT]: 2025-04-25 14:36:37 Age [y:d:h:m:s]: 00:012:00:13:59
Block: 1269213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8587 RingCT/type: yes/0
Extra: 011f383d986adb20c4e10282837c12388dce6e7b60ca4ca9a5c1be1139e046f03f0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad90a473ea6a78c89d8292ffc2b39733c24678722b22f042cfdfa9121a827a21 0.600000000000 1756448 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": 1269223, "vin": [ { "gen": { "height": 1269213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad90a473ea6a78c89d8292ffc2b39733c24678722b22f042cfdfa9121a827a21" } } ], "extra": [ 1, 31, 56, 61, 152, 106, 219, 32, 196, 225, 2, 130, 131, 124, 18, 56, 141, 206, 110, 123, 96, 202, 76, 169, 165, 193, 190, 17, 57, 224, 70, 240, 63, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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