Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0249bbaac7669b5126cba4847ae2d7c7223d1c311b363ec60f607200f5cc0b26

Tx prefix hash: 616c0d41537dac72c3dc94fe804cf0e7255440309809540d5f00b8bffa8325d3
Tx public key: f0fd958f258fd1f66e91e6affc329dc3675543ebdc6fe9c69df2f17cb4de7492
Timestamp: 1582520193 Timestamp [UCT]: 2020-02-24 04:56:33 Age [y:d:h:m:s]: 04:303:05:21:54
Block: 71519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109168 RingCT/type: yes/0
Extra: 01f0fd958f258fd1f66e91e6affc329dc3675543ebdc6fe9c69df2f17cb4de7492021100000001c71d3ff9000000000000000000

1 output(s) for total of 355.654792705000 dcy

stealth address amount amount idx
00: 4bf45e8612bfa8c1c0f7ff19d87c6d558e373ab6cc918ff1348d7a9e2366c5d1 355.654792705000 132064 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": 71529, "vin": [ { "gen": { "height": 71519 } } ], "vout": [ { "amount": 355654792705, "target": { "key": "4bf45e8612bfa8c1c0f7ff19d87c6d558e373ab6cc918ff1348d7a9e2366c5d1" } } ], "extra": [ 1, 240, 253, 149, 143, 37, 143, 209, 246, 110, 145, 230, 175, 252, 50, 157, 195, 103, 85, 67, 235, 220, 111, 233, 198, 157, 242, 241, 124, 180, 222, 116, 146, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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