Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f156dba5c044e34d54bf89267126dc04b6edc34f572ab71c7f847ac538fa904

Tx prefix hash: c32c73e899372df9c78861ab3272ab0b264f8a481b4bd17f721a22cdf74b3278
Tx public key: c0637b86a984de388017be2f8b977043ec0cd1721d4d6a36856a447d0895ba84
Timestamp: 1696910636 Timestamp [UCT]: 2023-10-10 04:03:56 Age [y:d:h:m:s]: 01:201:17:12:56
Block: 866339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405221 RingCT/type: yes/0
Extra: 01c0637b86a984de388017be2f8b977043ec0cd1721d4d6a36856a447d0895ba84021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.826911994000 dcy

stealth address amount amount idx
00: 45569125800fd4cc426be65d8f0348e7d4e3a190001b88c1e40b3c702f861a36 0.826911994000 1320921 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": 866349, "vin": [ { "gen": { "height": 866339 } } ], "vout": [ { "amount": 826911994, "target": { "key": "45569125800fd4cc426be65d8f0348e7d4e3a190001b88c1e40b3c702f861a36" } } ], "extra": [ 1, 192, 99, 123, 134, 169, 132, 222, 56, 128, 23, 190, 47, 139, 151, 112, 67, 236, 12, 209, 114, 29, 77, 106, 54, 133, 106, 68, 125, 8, 149, 186, 132, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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