Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b11a5cb83cc5d2b261226036c3a0285929e53264d00a69a3589131562d327d4

Tx prefix hash: ad492f0a08330846459eb36f387b844c106fc9d004fb295385520cf10fc95f6b
Tx public key: 4e2b8b38417dc6c2dc6267d2a010daf456419378bb90f8dbd3ae1726344d1d88
Timestamp: 1721317833 Timestamp [UCT]: 2024-07-18 15:50:33 Age [y:d:h:m:s]: 00:265:15:17:25
Block: 1068500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189762 RingCT/type: yes/0
Extra: 014e2b8b38417dc6c2dc6267d2a010daf456419378bb90f8dbd3ae1726344d1d88021100000002ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dfe8e3bc5a2b36d03ee30c4d9814c4cca7173c17d46870b73c9b09fc7144c0d 0.600000000000 1539579 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": 1068510, "vin": [ { "gen": { "height": 1068500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dfe8e3bc5a2b36d03ee30c4d9814c4cca7173c17d46870b73c9b09fc7144c0d" } } ], "extra": [ 1, 78, 43, 139, 56, 65, 125, 198, 194, 220, 98, 103, 210, 160, 16, 218, 244, 86, 65, 147, 120, 187, 144, 248, 219, 211, 174, 23, 38, 52, 77, 29, 136, 2, 17, 0, 0, 0, 2, 221, 211, 219, 145, 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