Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b50765537a4f8b5c908ff3e629da361d0cac8edc693d8959da9154d33036e39

Tx prefix hash: d5b2ef5127b55af8994542206f0611dc25074178098f0e50ae8700f7f83289af
Tx public key: 5cb0b9a4b030d087e8d9c1e581c1761252f58a7230ae4122c622eea43983909d
Timestamp: 1716489114 Timestamp [UCT]: 2024-05-23 18:31:54 Age [y:d:h:m:s]: 00:355:05:11:41
Block: 1028457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253901 RingCT/type: yes/0
Extra: 015cb0b9a4b030d087e8d9c1e581c1761252f58a7230ae4122c622eea43983909d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 915fbcf6a01974d8dea634d4afed7fff9e43cda8f16bf62ae659ca977221e014 0.600000000000 1496450 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": 1028467, "vin": [ { "gen": { "height": 1028457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "915fbcf6a01974d8dea634d4afed7fff9e43cda8f16bf62ae659ca977221e014" } } ], "extra": [ 1, 92, 176, 185, 164, 176, 48, 208, 135, 232, 217, 193, 229, 129, 193, 118, 18, 82, 245, 138, 114, 48, 174, 65, 34, 198, 34, 238, 164, 57, 131, 144, 157, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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