Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87111e5746407481705b49b030c57ff4355a4d2d3a0e2e9b733d0b471eaab91e

Tx prefix hash: 76bf6418b2b8a749f85cda0796dec47024df7e63cb838044613f6716ca7b5a37
Tx public key: 33e859643856f9ecd865b9b51e0116a4b0356e3f0926ed96e7979a8d16a509b9
Timestamp: 1731752954 Timestamp [UCT]: 2024-11-16 10:29:14 Age [y:d:h:m:s]: 00:217:11:32:40
Block: 1154906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155125 RingCT/type: yes/0
Extra: 0133e859643856f9ecd865b9b51e0116a4b0356e3f0926ed96e7979a8d16a509b9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e056de7a8b30f5e24556f063d92a03281c4667c81f8110539996f3deaf5ee34 0.600000000000 1640519 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": 1154916, "vin": [ { "gen": { "height": 1154906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e056de7a8b30f5e24556f063d92a03281c4667c81f8110539996f3deaf5ee34" } } ], "extra": [ 1, 51, 232, 89, 100, 56, 86, 249, 236, 216, 101, 185, 181, 30, 1, 22, 164, 176, 53, 110, 63, 9, 38, 237, 150, 231, 151, 154, 141, 22, 165, 9, 185, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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