Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88623d47923333ce9ea1538a791af0faabf3f0cd257da8e036bb42053f2a6eb5

Tx prefix hash: a0b10bcb92742920b06008cc86dee462528534448ca1293f5eece369df473af7
Tx public key: 4d7a4613563924d3a6fe10ed949e3f6355680844b5b870a602dec37c715f0d2c
Timestamp: 1704071971 Timestamp [UCT]: 2024-01-01 01:19:31 Age [y:d:h:m:s]: 01:108:13:32:49
Block: 925502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338713 RingCT/type: yes/0
Extra: 014d7a4613563924d3a6fe10ed949e3f6355680844b5b870a602dec37c715f0d2c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 567ad8a72707b2e2d47ea2c6c9feb9d79ba38ad49e8d89d8a0f9e661d7ab3106 0.600000000000 1383266 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": 925512, "vin": [ { "gen": { "height": 925502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "567ad8a72707b2e2d47ea2c6c9feb9d79ba38ad49e8d89d8a0f9e661d7ab3106" } } ], "extra": [ 1, 77, 122, 70, 19, 86, 57, 36, 211, 166, 254, 16, 237, 148, 158, 63, 99, 85, 104, 8, 68, 181, 184, 112, 166, 2, 222, 195, 124, 113, 95, 13, 44, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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