Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b6fe05a31b9e92be50581eab7134bfde02059886e0db719ef76211edd4bdf8

Tx prefix hash: e6da25ec075bf63b28b4384f899473cf010f99a87da59c89b3c9226ee690f261
Tx public key: 99221e3b29ecf125a7002274f88d8218fb251ae37559cf7b17f1bd8353ea8e9c
Timestamp: 1686934779 Timestamp [UCT]: 2023-06-16 16:59:39 Age [y:d:h:m:s]: 01:364:18:16:06
Block: 783672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521824 RingCT/type: yes/0
Extra: 0199221e3b29ecf125a7002274f88d8218fb251ae37559cf7b17f1bd8353ea8e9c021100000001faf35c9c000000000000000000

1 output(s) for total of 1.553708351000 dcy

stealth address amount amount idx
00: f9e72a330a5eec78f417a0996b691cf41e73c2274a02f3b2d0fc0c149358c478 1.553708351000 1233537 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": 783682, "vin": [ { "gen": { "height": 783672 } } ], "vout": [ { "amount": 1553708351, "target": { "key": "f9e72a330a5eec78f417a0996b691cf41e73c2274a02f3b2d0fc0c149358c478" } } ], "extra": [ 1, 153, 34, 30, 59, 41, 236, 241, 37, 167, 0, 34, 116, 248, 141, 130, 24, 251, 37, 26, 227, 117, 89, 207, 123, 23, 241, 189, 131, 83, 234, 142, 156, 2, 17, 0, 0, 0, 1, 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