Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dcad829b09393bbe5a227245db6311f66710d7a341eb22ac45e4602cfe6a5b6

Tx prefix hash: a7b4832bd60b2340958618a57f71d050235baafe1fbfa2de99583cf4d24da3f5
Tx public key: 62d6631012fd3dac0f6f3cdbf8664be9c62350b81af9d25d14a7ab32b121c57a
Timestamp: 1725904106 Timestamp [UCT]: 2024-09-09 17:48:26 Age [y:d:h:m:s]: 00:249:19:52:43
Block: 1106503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178420 RingCT/type: yes/0
Extra: 0162d6631012fd3dac0f6f3cdbf8664be9c62350b81af9d25d14a7ab32b121c57a02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0444d4fc3c8a494b8ceb8b20b463425597c8073fdc3b6ae298e4aff50dc227a0 0.600000000000 1584102 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": 1106513, "vin": [ { "gen": { "height": 1106503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0444d4fc3c8a494b8ceb8b20b463425597c8073fdc3b6ae298e4aff50dc227a0" } } ], "extra": [ 1, 98, 214, 99, 16, 18, 253, 61, 172, 15, 111, 60, 219, 248, 102, 75, 233, 198, 35, 80, 184, 26, 249, 210, 93, 20, 167, 171, 50, 177, 33, 197, 122, 2, 17, 0, 0, 0, 5, 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