Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93b5239ee03df5d25cea95212aaa226020cc22ef4fd979f1c98dab6f521027ae

Tx prefix hash: f66f314bf67868941ef6c5b6a5cf7155e7133f61070a07dc6d74985d368278e6
Tx public key: 7fd312e9e99e64c4b72b60b5aa81efa7c19ac542c103cae5d38380a4db23a4f0
Timestamp: 1718542870 Timestamp [UCT]: 2024-06-16 13:01:10 Age [y:d:h:m:s]: 00:333:09:35:11
Block: 1045493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238248 RingCT/type: yes/0
Extra: 017fd312e9e99e64c4b72b60b5aa81efa7c19ac542c103cae5d38380a4db23a4f002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab05670867dfb1e7df2311e392697bf7b65d8f1b6a82676bbef1118077c8497c 0.600000000000 1515080 of 15

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": 1045503, "vin": [ { "gen": { "height": 1045493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab05670867dfb1e7df2311e392697bf7b65d8f1b6a82676bbef1118077c8497c" } } ], "extra": [ 1, 127, 211, 18, 233, 233, 158, 100, 196, 183, 43, 96, 181, 170, 129, 239, 167, 193, 154, 197, 66, 193, 3, 202, 229, 211, 131, 128, 164, 219, 35, 164, 240, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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