Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb2b185ddb3ca2011042b8658d4d2787ea215b403982ef8ecfaf055d0cc4fe2

Tx prefix hash: 944efa6577d2fb7410efc20ccab40111a5834f7af519a21b161f750395998783
Tx public key: b31782501d08a0e2f8ef546a8b46a2a226cd4a43ed6ee974f4a1f8a87fbabac0
Timestamp: 1652867925 Timestamp [UCT]: 2022-05-18 09:58:45 Age [y:d:h:m:s]: 02:304:02:50:45
Block: 503510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737773 RingCT/type: yes/0
Extra: 01b31782501d08a0e2f8ef546a8b46a2a226cd4a43ed6ee974f4a1f8a87fbabac0021100000001a8c141c5000000000000000000

1 output(s) for total of 13.172328517000 dcy

stealth address amount amount idx
00: e8403f40e2c21ecef18f6ac7480e66aed0a6b7969791b04fa92d4ea2f275eaae 13.172328517000 928593 of 0

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": 503520, "vin": [ { "gen": { "height": 503510 } } ], "vout": [ { "amount": 13172328517, "target": { "key": "e8403f40e2c21ecef18f6ac7480e66aed0a6b7969791b04fa92d4ea2f275eaae" } } ], "extra": [ 1, 179, 23, 130, 80, 29, 8, 160, 226, 248, 239, 84, 106, 139, 70, 162, 162, 38, 205, 74, 67, 237, 110, 233, 116, 244, 161, 248, 168, 127, 186, 186, 192, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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