Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888afa605d2b0a4e456ef041a9aa5b50ea37c3270e926b8967d76507fe5e61f1

Tx prefix hash: 4d43d927f615d0b00a76221d2d98d77f434b3c502e5630510df5d89fe37debba
Tx public key: 024ba7d766b0ed3501d228a62eee52637d76459805e7e8f5055306aa3f3ab0db
Timestamp: 1698272795 Timestamp [UCT]: 2023-10-25 22:26:35 Age [y:d:h:m:s]: 01:167:08:23:39
Block: 877641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380609 RingCT/type: yes/0
Extra: 01024ba7d766b0ed3501d228a62eee52637d76459805e7e8f5055306aa3f3ab0db021100000005faf35c9c000000000000000000

1 output(s) for total of 0.758596888000 dcy

stealth address amount amount idx
00: f3075bd2f390a96601437826c9e8002894d8366b90f0009507b0feabf15691a0 0.758596888000 1333027 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": 877651, "vin": [ { "gen": { "height": 877641 } } ], "vout": [ { "amount": 758596888, "target": { "key": "f3075bd2f390a96601437826c9e8002894d8366b90f0009507b0feabf15691a0" } } ], "extra": [ 1, 2, 75, 167, 215, 102, 176, 237, 53, 1, 210, 40, 166, 46, 238, 82, 99, 125, 118, 69, 152, 5, 231, 232, 245, 5, 83, 6, 170, 63, 58, 176, 219, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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