Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abebf094ceb850d4e01681b7b5b095b4cb5ede08c60317ede1345fadf570f474

Tx prefix hash: a1cc86db2b927cfb570fffe78953de4b39f9ca3a208c75048281fcda0d64ace4
Tx public key: 6a346e451e3c36543c194f4fa27922ea660b2a3506a66962c7422de4cd4dfffa
Timestamp: 1722141147 Timestamp [UCT]: 2024-07-28 04:32:27 Age [y:d:h:m:s]: 00:249:21:49:36
Block: 1075304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178507 RingCT/type: yes/0
Extra: 016a346e451e3c36543c194f4fa27922ea660b2a3506a66962c7422de4cd4dfffa021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49685d9275d2b65f0da99244cfc117104dad6ee1b21affc0651f3a9ae7e512fa 0.600000000000 1547829 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": 1075314, "vin": [ { "gen": { "height": 1075304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49685d9275d2b65f0da99244cfc117104dad6ee1b21affc0651f3a9ae7e512fa" } } ], "extra": [ 1, 106, 52, 110, 69, 30, 60, 54, 84, 60, 25, 79, 79, 162, 121, 34, 234, 102, 11, 42, 53, 6, 166, 105, 98, 199, 66, 45, 228, 205, 77, 255, 250, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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