Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653b36a1bc4d6a302d9afcd87eb5055fb028ac13ac6f9025479bca8a343fa5ba

Tx prefix hash: 7dca46729436ca2e9c6044a62e5861281f5fd3a40efd5e3fe3a310aa8a02804d
Tx public key: 7a7d21be12ae4ed108fac9940402a492a853e4c72e0db30b9d4dea4b727c9fee
Timestamp: 1700498728 Timestamp [UCT]: 2023-11-20 16:45:28 Age [y:d:h:m:s]: 01:095:15:22:07
Block: 895877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329485 RingCT/type: yes/0
Extra: 017a7d21be12ae4ed108fac9940402a492a853e4c72e0db30b9d4dea4b727c9fee02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.660066349000 dcy

stealth address amount amount idx
00: da9aed06a489ed387cd9fba64a741703f70452ff54ab15aed4decf6b73ccbe3b 0.660066349000 1352124 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": 895887, "vin": [ { "gen": { "height": 895877 } } ], "vout": [ { "amount": 660066349, "target": { "key": "da9aed06a489ed387cd9fba64a741703f70452ff54ab15aed4decf6b73ccbe3b" } } ], "extra": [ 1, 122, 125, 33, 190, 18, 174, 78, 209, 8, 250, 201, 148, 4, 2, 164, 146, 168, 83, 228, 199, 46, 13, 179, 11, 157, 77, 234, 75, 114, 124, 159, 238, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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