Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86715a366bd942226c623e2fef0591aa291362dfab625d46daf84d406f381ab8

Tx prefix hash: 2be1c1f43da09e1a47aa7d9b09fd0a70a79f835ca927d5522c647186d43400fb
Tx public key: 0ef683c923652df70d04323bbde57905c429cf6c107cbf16e862fef4773ebe0f
Timestamp: 1699558580 Timestamp [UCT]: 2023-11-09 19:36:20 Age [y:d:h:m:s]: 01:108:06:25:27
Block: 888091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338519 RingCT/type: yes/0
Extra: 010ef683c923652df70d04323bbde57905c429cf6c107cbf16e862fef4773ebe0f021100000004faf35c9c000000000000000000

1 output(s) for total of 0.700464055000 dcy

stealth address amount amount idx
00: 9e6179de973f3b16759b2c8602926ce331f600c228bc872f709bcd0943b3c655 0.700464055000 1344010 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": 888101, "vin": [ { "gen": { "height": 888091 } } ], "vout": [ { "amount": 700464055, "target": { "key": "9e6179de973f3b16759b2c8602926ce331f600c228bc872f709bcd0943b3c655" } } ], "extra": [ 1, 14, 246, 131, 201, 35, 101, 45, 247, 13, 4, 50, 59, 189, 229, 121, 5, 196, 41, 207, 108, 16, 124, 191, 22, 232, 98, 254, 244, 119, 62, 190, 15, 2, 17, 0, 0, 0, 4, 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