Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9aaa4cbc902ab8979d44d3a2738efcdabc660b3f7c9ae7a1b808a21113203ba

Tx prefix hash: 438dd3e0fb0eb1a3764946620a59fd334c3f92c9ac660b0ad56be7f175a3440b
Tx public key: 53eed5a1a8c7b2256285f218d84e3d65e3b7b47192cd0074485fad49b980ce1c
Timestamp: 1723179581 Timestamp [UCT]: 2024-08-09 04:59:41 Age [y:d:h:m:s]: 00:251:01:14:35
Block: 1083917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179319 RingCT/type: yes/0
Extra: 0153eed5a1a8c7b2256285f218d84e3d65e3b7b47192cd0074485fad49b980ce1c02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472502cf0ece059149d8c19d9b68f31d223b0bd1219708571f27a8dc10a6853f 0.600000000000 1558004 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": 1083927, "vin": [ { "gen": { "height": 1083917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472502cf0ece059149d8c19d9b68f31d223b0bd1219708571f27a8dc10a6853f" } } ], "extra": [ 1, 83, 238, 213, 161, 168, 199, 178, 37, 98, 133, 242, 24, 216, 78, 61, 101, 227, 183, 180, 113, 146, 205, 0, 116, 72, 95, 173, 73, 185, 128, 206, 28, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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