Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250bc605c36cd50538a6b5d3b76cf327cbbee984321e585b3bbf60d9cc67d895

Tx prefix hash: 56380923cc2065b1471486605d3f44b014803cb7c7050b1aed05cf63d8532792
Tx public key: 66b5eea8fd62d028790ab4d1d15205721884ae501c441641db495c2cb3082acc
Timestamp: 1633079959 Timestamp [UCT]: 2021-10-01 09:19:19 Age [y:d:h:m:s]: 03:095:21:11:21
Block: 344369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845485 RingCT/type: yes/0
Extra: 0166b5eea8fd62d028790ab4d1d15205721884ae501c441641db495c2cb3082acc0211000000345410958b000000000000000000

1 output(s) for total of 44.358622847000 dcy

stealth address amount amount idx
00: dec68e4249ea3c6bc05c4cbda6a86db54b4af7e0b5f3b0bf00c102047f5a0520 44.358622847000 706627 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": 344379, "vin": [ { "gen": { "height": 344369 } } ], "vout": [ { "amount": 44358622847, "target": { "key": "dec68e4249ea3c6bc05c4cbda6a86db54b4af7e0b5f3b0bf00c102047f5a0520" } } ], "extra": [ 1, 102, 181, 238, 168, 253, 98, 208, 40, 121, 10, 180, 209, 209, 82, 5, 114, 24, 132, 174, 80, 28, 68, 22, 65, 219, 73, 92, 44, 179, 8, 42, 204, 2, 17, 0, 0, 0, 52, 84, 16, 149, 139, 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